Finding ID | Version | Rule ID | IA Controls | Severity |
---|---|---|---|---|
V-57549 | SRG-APP-000223-AS-000150 | SV-71825r2_rule | Medium |
Description |
---|
Unique session IDs are the opposite of sequentially generated session IDs, which can be easily guessed by an attacker. Unique session identifiers help to reduce predictability of session identifiers. Unique session IDs address man-in-the-middle attacks, including session hijacking or insertion of false information into a session. If the attacker is unable to identify or guess the session information related to pending application traffic, they will have more difficulty in hijacking the session or otherwise manipulating valid sessions. Application servers must generate a unique session identifier for each application session so as to prevent session hijacking. |
STIG | Date |
---|---|
Application Server Security Requirements Guide | 2018-09-13 |
Check Text ( C-58257r1_chk ) |
---|
Review the application server configuration to determine if the application server generates a unique session identifier for each session. Request an administrator log onto the server and view the logs to verify a unique session identifier was assigned to the session. If the application server does not generate a unique session identifier for each session, this is a finding. |
Fix Text (F-62617r1_fix) |
---|
Configure the application server to generate a unique session identifier for each session. |